Methods and apparatuses to provide geofence-based reportable estimates

ABSTRACT

Systems, methods, apparatus, and computer program products are provided for estimating taxes. In one embodiment, the location of a vehicle can be monitored by a variety of computing entities. By using the vehicle&#39;s location, it can be determined when the vehicle enters and/or exits defined geofences. After a determination that the vehicle has entered or exited a defined geofenced area, telematics data can be collected and used to estimate taxes, such as road use taxes and fuel use taxes.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Application No.61/511,884, filed Jul. 26, 2011, which is hereby incorporated herein inits entirety by reference. The present application is a Continuation ofU.S. application Ser. No. 13/472,073, filed May 5, 2015 and titled“METHODS AND APPARATUSES TO PROVIDE GEOFENCE-BASED REPORTABLEESTIMATES,” which itself claims the benefit of related to U.S.Application Ser. No. 61/511,884 entitled “GEOFENCE-BASED TAX ESTIMATES,”filed Jul. 26, 2011 which the entire contents of each of the foregoingbeing incorporated by reference in their entirety.

BACKGROUND

Various jurisdictions impose road use taxes and fuel use taxes oncertain types of vehicles. Currently, the methods of tracking one's roaduse and fuel use within a jurisdiction are manual in nature. Thus, aneed exists for more efficiently determining one's road use and fuel usewithin a jurisdiction to determine any applicable taxes.

BRIEF SUMMARY

In general, embodiments of the present invention provide systems,methods, apparatus, and computer program products for estimating taxes.

In accordance with one aspect, a method for estimating taxes isprovided. In one embodiment, the method comprises (1) determining anestimated amount of fuel consumed by a vehicle while operated within oneor more geofenced areas; and (2) determining an estimated fuel use taxfor operating the vehicle within the one or more geofenced areas,wherein the estimated fuel use tax is based at least in part on theestimated amount of fuel consumed by the vehicle while operated withinthe one or more geofenced areas.

In accordance with another aspect, a method for estimating taxes isprovided. In one embodiment, the method comprises (1) determining anestimated distance traversed by a vehicle while operated within one ormore geofenced areas; and (2) determining an estimated road use tax foroperating the vehicle within the one or more geofenced areas, whereinthe estimated road use tax is based at least in part on the estimateddistance traversed by the vehicle while operated within the geofencedarea.

In accordance with yet another aspect, a method for estimating taxes isprovided. In one embodiment, the method comprises (1) monitoring thelocation of a vehicle to determine whether the vehicle has entered ageofenced area; (2) after determining the vehicle has entered thegeofenced area, identifying first fuel data associated with the vehicle;(3) monitoring the location of the vehicle to determine whether thevehicle has exited the geofenced area; and (4) after determining thevehicle has exited the geofenced area, identifying second fuel dataassociated with the vehicle. In one embodiment, the method may alsocomprise (5) determining an estimated amount of fuel consumed, based atleast in part on the first fuel data and the second fuel data, by thevehicle while operated within the geofenced area; and (6) determining anestimated fuel use tax for operating the vehicle within the geofencedarea, wherein the estimated fuel use tax is based at least in part onthe estimated amount of fuel consumed by the vehicle while operatedwithin the geofenced area.

In accordance with still another aspect, a method for estimating taxesis provided. In one embodiment, the method comprises (1) monitoring thelocation of a vehicle to determine whether the vehicle has entered ageofenced area; (2) after determining the vehicle has entered thegeofenced area, identifying first distance data associated with thevehicle; (3) electronically monitoring the location of the vehicle todetermine whether the vehicle has exited the geofenced area; and (4)after determining the vehicle has exited the geofenced area, identifyingsecond distance data associated with the vehicle. In one embodiment, themethod may also comprise (5) determining an estimated distancetraversed, based at least in part on the first distance data and thesecond distance data, by the vehicle while operated within the geofencedarea; and (6) determining an estimated road use tax for operating thevehicle within the geofenced area, wherein the estimated road use tax isbased at least in part on the estimated distance traversed by thevehicle while operated within the geofenced area.

In accordance with one aspect, a system comprising one or more memorystorage areas and one or more processors is provided. In one embodiment,the system is configured to at least (1) determine an estimated amountof fuel consumed by a vehicle while operated within one or moregeofenced areas; and (2) determine an estimated fuel use tax foroperating the vehicle within the one or more geofenced areas, whereinthe estimated fuel use tax is based at least in part on the estimatedamount of fuel consumed by the vehicle while operated within the one ormore geofenced areas.

In accordance with another aspect, a system comprising one or morememory storage areas and one or more processors is provided. In oneembodiment, the system is configured to at least (1) determine anestimated distance traversed by a vehicle while operated within one ormore geofenced areas; and (2) determine an estimated road use tax foroperating the vehicle within the one or more geofenced areas, whereinthe estimated road use tax is based at least in part on the estimateddistance traversed by the vehicle while operated within the geofencedarea.

In accordance with yet another aspect, a system comprising one or morememory storage areas and one or more processors is provided. In oneembodiment, the system is configured to at least (1) monitor thelocation of a vehicle to determine whether the vehicle has entered ageofenced area; (2) after determining the vehicle has entered thegeofenced area, identify first fuel data associated with the vehicle;(3) monitor the location of the vehicle to determine whether the vehiclehas exited the geofenced area; and (4) after determining the vehicle hasexited the geofenced area, identify second fuel data associated with thevehicle. In one embodiment, the system may also be configured to atleast (5) determine an estimated amount of fuel consumed, based at leastin part on the first fuel data and the second fuel data, by the vehiclewhile operated within the geofenced area; and (6) determine an estimatedfuel use tax for operating the vehicle within the geofenced area,wherein the estimated fuel use tax is based at least in part on theestimated amount of fuel consumed by the vehicle while operated withinthe geofenced area.

In accordance with still another aspect, a system comprising one or morememory storage areas and one or more processors is provided. In oneembodiment, the system is configured to at least (1) monitor thelocation of a vehicle to determine whether the vehicle has entered ageofenced area; (2) after determining the vehicle has entered thegeofenced area, identify first distance data associated with thevehicle; (3) monitor the location of the vehicle to determine whetherthe vehicle has exited the geofenced area; and (4) after determining thevehicle has exited the geofenced area, identify second distance dataassociated with the vehicle. In one embodiment, the system may also beconfigured to at least (5) determine an estimated distance traversed,based at least in part on the first distance data and the seconddistance data, by the vehicle while operated within the geofenced area;and (6) determine an estimated road use tax for operating the vehiclewithin the geofenced area, wherein the estimated road use tax is basedat least in part on the estimated distance traversed by the vehiclewhile operated within the geofenced area.

In accordance with one aspect, a computer program product for processinga claim is provided. The computer program product may comprise at leastone computer-readable storage medium having computer-readable programcode portions stored therein, the computer-readable program codeportions comprising executable portions configured to (1) determine anestimated amount of fuel consumed by a vehicle while operated within oneor more geofenced areas; and (2) determine an estimated fuel use tax foroperating the vehicle within the one or more geofenced areas, whereinthe estimated fuel use tax is based at least in part on the estimatedamount of fuel consumed by the vehicle while operated within the one ormore geofenced areas.

In accordance with another aspect, a computer program product forprocessing a claim is provided. The computer program product maycomprise at least one computer-readable storage medium havingcomputer-readable program code portions stored therein, thecomputer-readable program code portions comprising executable portionsconfigured to (1) determine an estimated distance traversed by a vehiclewhile operated within one or more geofenced areas; and (2) determine anestimated road use tax for operating the vehicle within the one or moregeofenced areas, wherein the estimated road use tax is based at least inpart on the estimated distance traversed by the vehicle while operatedwithin the geofenced area.

In accordance with yet another aspect, a computer program product forprocessing a claim is provided. The computer program product maycomprise at least one computer-readable storage medium havingcomputer-readable program code portions stored therein, thecomputer-readable program code portions comprising executable portionsconfigured to (1) monitor the location of a vehicle to determine whetherthe vehicle has entered a geofenced area; (2) after determining thevehicle has entered the geofenced area, identify first fuel dataassociated with the vehicle; (3) monitor the location of the vehicle todetermine whether the vehicle has exited the geofenced area; and (4)after determining the vehicle has exited the geofenced area, identifysecond fuel data associated with the vehicle. In one embodiment, thesystem may also be configured to at least (5) determine an estimatedamount of fuel consumed, based at least in part on the first fuel dataand the second fuel data, by the vehicle while operated within thegeofenced area; and (6) determine an estimated fuel use tax foroperating the vehicle within the geofenced area, wherein the estimatedfuel use tax is based at least in part on the estimated amount of fuelconsumed by the vehicle while operated within the geofenced area.

In accordance with still another aspect, a computer program product forprocessing a claim is provided. The computer program product maycomprise at least one computer-readable storage medium havingcomputer-readable program code portions stored therein, thecomputer-readable program code portions comprising executable portionsconfigured to (1) monitor the location of a vehicle to determine whetherthe vehicle has entered a geofenced area; (2) after determining thevehicle has entered the geofenced area, identify first distance dataassociated with the vehicle; (3) monitor the location of the vehicle todetermine whether the vehicle has exited the geofenced area; and (4)after determining the vehicle has exited the geofenced area, identifysecond distance data associated with the vehicle. In one embodiment, thesystem may also be configured to at least (5) determine an estimateddistance traversed, based at least in part on the first distance dataand the second distance data, by the vehicle while operated within thegeofenced area; and (6) determine an estimated road use tax foroperating the vehicle within the geofenced area, wherein the estimatedroad use tax is based at least in part on the estimated distancetraversed by the vehicle while operated within the geofenced area.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)

Reference will be made to the accompanying drawings, which are notnecessarily drawn to scale, and wherein:

FIG. 1 is a diagram of a system that can be used to practice variousembodiments of the present invention.

FIG. 2 includes a diagram of a data collection device that may be usedin association with certain embodiments of the present invention.

FIG. 3 is a schematic of a monitoring server in accordance with certainembodiments of the present invention.

FIG. 4 is a schematic of a portable device in accordance with certainembodiments of the present invention.

FIGS. 5 and 14 are flowcharts illustrating operations and processes thatcan be used in accordance with various embodiments of the presentinvention.

FIGS. 6A and 6B illustrate exemplary road use tax rates that can be usedin accordance with various embodiments of the present invention.

FIG. 7 illustrates an exemplary road use tax schedule that can be usedin accordance with various embodiments of the present invention.

FIG. 8 illustrates exemplary fuel use tax rates that can be used inaccordance with various embodiments of the present invention.

FIG. 9 illustrates an exemplary fuel use tax schedule that can be usedin accordance with various embodiments of the present invention.

FIGS. 10 and 11 illustrate exemplary electronic records that can be usedin accordance with various embodiments of the present invention.

FIGS. 12A, 12B, 12C, 13A, 13B, and 13C illustrate roads along which avehicle may travel in accordance with various embodiments of the presentinvention.

DETAILED DESCRIPTION

Various embodiments of the present invention now will be described morefully hereinafter with reference to the accompanying drawings, in whichsome, but not all embodiments of the inventions are shown. Indeed, theseinventions may be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein; rather, theseembodiments are provided so that this disclosure will satisfy applicablelegal requirements. The term “or” is used herein in both the alternativeand conjunctive sense, unless otherwise indicated. The terms“illustrative” and “exemplary” are used to be examples with noindication of quality level. Like numbers refer to like elementsthroughout.

I. Methods, Apparatus, Systems, and Computer Program Products

As should be appreciated, various embodiments may be implemented invarious ways, including as methods, apparatus, systems, or computerprogram products. Accordingly, various embodiments may take the form ofan entirely hardware embodiment or an embodiment in which a processor isprogrammed to perform certain steps. Furthermore, variousimplementations may take the form of a computer program product on acomputer-readable storage medium having computer-readable programinstructions embodied in the storage medium. Any suitablecomputer-readable storage medium may be utilized including hard disks,CD-ROMs, optical storage devices, or magnetic storage devices.

Various embodiments are described below with reference to block diagramsand flowchart illustrations of methods, apparatus, systems, and computerprogram products. It should be understood that each block of the blockdiagrams and flowchart illustrations, respectively, may be implementedin part by computer program instructions, e.g., as logical steps oroperations executing on a processor in a computing system. Thesecomputer program instructions may be loaded onto a computer, such as aspecial purpose computer or other programmable data processing apparatusto produce a specifically-configured machine, such that the instructionswhich execute on the computer or other programmable data processingapparatus implement the functions specified in the flowchart block orblocks.

These computer program instructions may also be stored in acomputer-readable memory that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including computer-readableinstructions for implementing the functionality specified in theflowchart block or blocks. The computer program instructions may also beloaded onto a computer or other programmable data processing apparatusto cause a series of operational steps to be performed on the computeror other programmable apparatus to produce a computer-implementedprocess such that the instructions that execute on the computer or otherprogrammable apparatus provide operations for implementing the functionsspecified in the flowchart block or blocks.

Accordingly, blocks of the block diagrams and flowchart illustrationssupport various combinations for performing the specified functions,combinations of operations for performing the specified functions, andprogram instructions for performing the specified functions. It shouldalso be understood that each block of the block diagrams and flowchartillustrations, and combinations of blocks in the block diagrams andflowchart illustrations, can be implemented by special purposehardware-based computer systems that perform the specified functions oroperations, or combinations of special purpose hardware and computerinstructions.

II. Exemplary System Architecture

FIG. 1 provides an illustration of a system that can be used inconjunction with various embodiments of the present invention. As shownin FIG. 1, the system may include one or more vehicles 100, one or moreportable devices 105, one or more monitoring servers 110, one or moreGlobal Positioning System (GPS) satellites 115, one or more locationsensors 120, one or more telematics sensors 125, one or more datacollection devices 130, one or more networks 135, and/or the like. Eachof the components of the system may be in electronic communication with,for example, one another over the same or different wireless or wirednetworks including, for example, a wired or wireless Personal AreaNetwork (PAN), Local Area Network (LAN), Metropolitan Area Network(MAN), Wide Area Network (WAN), or the like. Additionally, while FIG. 1illustrates certain system entities as separate, standalone entities,the various embodiments are not limited to this particular architecture.

a. Exemplary Vehicle

In various embodiments, the vehicle 100 (such as a delivery vehicle,truck, tractor, or other self-propelled vehicle) may include one or morelocation sensors 120, one or more telematics sensors 125, one or moredata collection devices 130, and/or the like.

Reference is now made to FIG. 2, which provides a block diagram of anexemplary data collection device 130. The data collection device 130 maycollect location and telematics data and transmit the data to theportable device 105 and/or the monitoring server 110 via one of severalcommunication methods.

In one embodiment, the data collection device 130 may include, beassociated with, or be in communication with one or more processors 200,one or more location-determining devices or one or more location sensors120 (e.g., Global Navigation Satellite System (GNSS) sensors), one ormore telematics sensors 125, one or more real-time clocks 215, a J-Busprotocol architecture, one or more electronic control modules (ECM) 245,one or more communication ports 230 for receiving data from varioussensors (e.g., via a CAN-bus), one or more communication ports 205 fortransmitting data, one or more radio frequency identification (RFID)tags 250, one or more power sources 220, one or more data radios 235 forcommunication with a variety of communication networks, one or morememory modules 210, and one or more programmable logic controllers (PLC)225. It should be noted that many of these components may be located inthe vehicle 100 but external to the data collection device 130.

In one embodiment, the one or more location sensors 120 may be one ofseveral components in communication with or available to the datacollection device 130. Moreover, the one or more location sensors 120may be compatible with a Low Earth Orbit (LEO) satellite system or aDepartment of Defense (DOD) satellite system. Alternatively,triangulation may be used in connection with a device associated with aparticular vehicle and/or the vehicle's driver and with variouscommunication points (e.g., cellular towers or Wi-Fi access points)positioned at various locations throughout a geographic area to monitorthe location of the vehicle 100 and/or its driver. The one or morelocation sensors 120 may be used to receive latitude, longitude,altitude, geocode, course, position, time, and/or speed data (e.g.,location data). The one or more location sensors 120 may alsocommunicate with the monitoring server 110, the data collection device130, and/or a similar network entity.

As indicated, in addition to the one or more location sensors 120, thedata collection device 130 may include and/or be associated with one ormore telematics sensors 125. For example, the telematics sensors 125 mayinclude vehicle sensors, such as engine, fuel, odometer, hubometer, tirepressure, location, weight, emissions, door, and speed sensors. Thetelematics data may include, but is not limited to, speed data,emissions data, RPM data, tire pressure data, oil pressure data, seatbelt usage data, distance data, fuel data, idle data, and/or the like.The telematics sensors 125 may include environmental sensors, such asair quality sensors, temperature sensors, and/or the like. Thus, thetelematics data may also include carbon monoxide (CO), nitrogen oxides(NOx), sulfur oxides (SOx), ozone (O₃), hydrogen sulfide (H₂S) and/orammonium (NH₄) data and/or meteorological data.

In one embodiment, the ECM 245 may be one of several components incommunication with and/or available to the data collection device 130.The ECM 245, which may be a scalable and subservient device to the datacollection device 130, may have data processing capability to decode andstore analog and digital inputs from vehicle systems and sensors. TheECM 245 may further have data processing capability to collect andpresent vehicle data to the J-Bus (which may allow transmission to thedata collection device 130), and output standard vehicle diagnosticcodes when received from a vehicle's J-Bus-compatible on-boardcontrollers 240 and/or sensors.

As indicated, a communication port 230 may be one of several componentsavailable in the data collection device 130. Embodiments of thecommunication port 230 may include an Infrared Data Association (IrDA)communication port, a data radio, and/or a serial port. Thecommunication port 230 may receive instructions for the data collectiondevice 130. These instructions may be specific to the vehicle 100 inwhich the data collection device 130 is installed, specific to thegeographical area in which the vehicle 100 will be traveling, and/orspecific to the function the vehicle 100 serves within the fleet. In oneembodiment, the data radio 235 may be configured to communicate with awireless wide area network (WWAN), wireless local area network (WLAN),wireless personal area network (WPAN), or any combination thereof. Forexample, the data radio 235 may communicate via various wirelessprotocols, such as 802.11, general packet radio service (GPRS),Universal Mobile Telecommunications System (UMTS), Code DivisionMultiple Access 2000 (CDMA2000), Wideband Code Division Multiple Access(WCDMA), Time Division-Synchronous Code Division Multiple Access(TD-SCDMA), Long Term Evolution (LTE), Evolved Universal TerrestrialRadio Access Network (E-UTRAN), IEEE 802.11 (Wi-Fi), 802.16 (WiMAX),ultra wideband (UWB), infrared (IR) protocols, Bluetooth protocols,wireless universal serial bus (USB) protocols, and/or any other wirelessprotocol. Via these communication standards and protocols, the datacollection device 130 can communicate with various other entities.

In one embodiment, one or more RFID tags 250 may be one of severalcomponents available for use with the data collection device 130. Oneembodiment of the one or more RFID tags 250 may include active RFIDtags, each of which may comprise at least one of the following: (1) aninternal clock; (2) a memory; (3) a microprocessor; and (4) at least oneinput interface for connecting with sensors located in the vehicle 100and/or the data collection device 130. Another embodiment of the RFIDtags 250 may be passive RFID tags.

b. Exemplary Monitoring Server

FIG. 3 provides a schematic of a monitoring server 110 according to oneembodiment of the present invention. In general, the term “server” mayrefer to, for example, any computer, computing device, mobile phone,desktop, notebook or laptop, distributed system, server, blade, gateway,switch, processing device, or combination of processing devices adaptedto perform the functions described herein. As will be understood fromthis figure, in one embodiment, the monitoring server 110 may include aprocessor 305 that communicates with other elements within themonitoring server 110 via a system interface or bus 361. The processor305 may be embodied in a number of different ways. For example, theprocessor 305 may be embodied as one or more processing elements, one ormore microprocessors with accompanying digital signal processors, one ormore processors without an accompanying digital signal processors, oneor more coprocessors, one or more multi-core processors, one or morecontrollers, and/or various other processing devices includingintegrated circuits such as, for example, an application specificintegrated circuit (ASIC), a field programmable gate array (FPGA), ahardware accelerator, and/or the like.

In an exemplary embodiment, the processor 305 may be configured toexecute instructions stored in the device memory or otherwise accessibleto the processor 305. As such, whether configured by hardware orsoftware methods, or by a combination thereof, the processor 305 mayrepresent an entity capable of performing operations according toembodiments of the present invention when configured accordingly. Adisplay device/input device 364 for receiving and displaying data mayalso be included in or associated with the monitoring server 110. Thedisplay device/input device 364 may be, for example, a keyboard orpointing device that is used in combination with a monitor. Themonitoring server 110 may further include transitory and non-transitorymemory 363, which may include both random access memory (RAM) 367 andread only memory (ROM) 365. The monitoring server's ROM 365 may be usedto store a basic input/output system (BIOS) 326 containing the basicroutines that help to transfer information to the different elementswithin the monitoring server 110.

In addition, in one embodiment, the monitoring server 110 may include atleast one storage device 368, such as a hard disk drive, a CD drive, aDVD drive, and/or an optical disk drive for storing information onvarious computer-readable media. The storage device(s) 368 and itsassociated computer-readable media may provide nonvolatile storage. Thecomputer-readable media described above could be replaced by any othertype of computer-readable media, such as embedded or removablemultimedia memory cards (MMCs), secure digital (SD) memory cards, MemorySticks, electrically erasable programmable read-only memory (EEPROM),flash memory, hard disk, and/or the like. Additionally, each of thesestorage devices 368 may be connected to the system bus 361 by anappropriate interface.

Furthermore, a number of program modules may be stored by the variousstorage devices 368 and/or within RAM 367. Such program modules mayinclude an operating system 380, a collection module 370, a locationmodule 360, and a trigger module 350. As discussed in greater detailbelow, these modules may control certain aspects of the operation of themonitoring server 110 with the assistance of the processor 305 andoperating system 380—although their functionality need not bemodularized. In addition to the program modules, the monitoring server110 may store and/or be in communication with one or more databases,such as database 340.

Also located within and/or associated with the monitoring server 110, inone embodiment, is a network interface 374 for interfacing with variouscomputing entities. This communication may be via the same or differentwired or wireless networks (or a combination of wired and wirelessnetworks), as discussed above. For instance, the communication may beexecuted using a wired data transmission protocol, such as fiberdistributed data interface (FDDI), digital subscriber line (DSL),Ethernet, asynchronous transfer mode (ATM), frame relay, data over cableservice interface specification (DOCSIS), and/or any other wiredtransmission protocol. Similarly, the monitoring server 110 may beconfigured to communicate via wireless external communication networksusing any of a variety of protocols, such as 802.11, GPRS, UMTS,CDMA2000, WCDMA, TD-SCDMA, LTE, E-UTRAN, Wi-Fi, WiMAX, UWB, and/or anyother wireless protocol.

It will be appreciated that one or more of the monitoring server's 110components may be located remotely from other monitoring server 110components. Furthermore, one or more of the components may be combinedand additional components performing functions described herein may beincluded in the monitoring server 110.

c. Exemplary Portable Device

With respect to the portable device 105, FIG. 4 provides an illustrativeschematic representative of a portable device 105 that can be used inconjunction with the embodiments of the present invention (e.g., aportable device 105 carried by a delivery driver). As shown in FIG. 4,the portable device 105 can include an antenna 412, a transmitter 404, areceiver 406, and a processing device 408, e.g., a processor,controller, and/or the like, that provides signals to and receivessignals from the transmitter 404 and receiver 406, respectively.

The signals provided to and received from the transmitter 404 and thereceiver 406, respectively, may include signaling information inaccordance with an air interface standard of applicable wireless (orwired) systems. In this regard, the portable device 105 may be capableof operating with one or more air interface standards, communicationprotocols, modulation types, and access types. More particularly, theportable device 105 may operate in accordance with any of a number ofsecond-generation (2G) communication protocols, third-generation (3G)communication protocols, and/or the like. Further, for example, theportable device 105 may operate in accordance with any of a number ofdifferent wireless networking techniques, such as GPRS, UMTS, CDMA2000,WCDMA, TD-SCDMA, LTE, E-UTRAN, Wi-Fi, WiMAX, UWB, and/or any otherwireless protocol. Via these communication standards and protocols, theportable device 105 can communicate with the monitoring server 110and/or various other entities.

The portable device 105 may also comprise a user interface (that caninclude a display 416 coupled to a processing device 408) and/or a userinput interface (coupled to the processing device 408). The user inputinterface can comprise any of a number of devices allowing the portabledevice 105 to receive data, such as a keypad 418, a touch display (notshown), barcode reader (not shown), RFID tag reader (not shown), and/orother input device. In embodiments including a keypad 418, the keypad418 can include the conventional numeric (0-9) and related keys (#, *),and other keys used for operating the portable device 105 and mayinclude a full set of alphabetic keys or set of keys that may beactivated to provide a full set of alphanumeric keys. In addition toproviding input, the user input interface can be used, for example, toactivate and/or deactivate certain functions, such as screen saversand/or sleep modes. Although not shown, the portable device 105 may alsoinclude a battery, such as a vibrating battery pack, for powering thevarious circuits that are required to operate the portable device 105,as well as optionally providing mechanical vibration as a detectableoutput.

The portable device 105 can also include volatile memory 422 and/ornon-volatile memory 424, which can be embedded or may be removable. Forexample, the non-volatile memory may be embedded or removable MMCs, SDmemory cards, Memory Sticks, EEPROM, flash memory, hard disk, and/or thelike. The memory can store any of a number of pieces or amount ofinformation and data used by the portable device 105 to implement thefunctions of the portable device 105. The memory can also store content,such as computer program code for an application and/or other computerprograms.

The portable device 105 may also include a GPS module adapted toacquire, for example, latitude, longitude, altitude, geocode, course,speed, universal time (UTC), date, and/or telematics information/data.In one embodiment, the GPS module acquires data, sometimes known asephemeris data, by identifying the number of satellites in view and therelative positions of those satellites. In addition, data regarding, forexample, heading and estimated time of arrival (ETA) can also becaptured, which enhances the determination of the position of the GPSmodule.

III. Exemplary System Operation

Reference will now be made to FIGS. 5, 6A, 6B, and 7-10. FIGS. 5 and 14illustrate operations and processes that can be performed forgeofence-based tax estimates. FIGS. 6A, 6B, and 8 illustrate exemplarytax rates, and FIGS. 7 and 9 illustrate exemplary tax schedules. FIGS.10 and 11 illustrate exemplary electronic records. FIGS. 12A, 12B, 12C,13A, 13B, and 13C illustrate roads along which a vehicle may travel.

a. Exemplary Taxes

As will be recognized, the operation of vehicles 100 within specificjurisdictions (e.g., countries, regions, states, counties, cities,and/or towns) may subject one to various taxes, examples of which areprovided below.

i. Road Use Taxes (RUTs)

In one embodiment, certain jurisdictions (e.g., countries, regions,states, counties, cities, and/or towns) may impose a road use tax (RUT)on particular types of vehicles 100 operating within theirjurisdictions. For instance, the RUT may be imposed on qualifiedvehicles 100 for their use of certain public roads. The RUT may excludeuse on non-public roads, such as parking lots, military bases, vehiclestaging areas, driveways, private land areas, and/or the like. By way ofexample, New York State may impose an RUT on qualified vehicles 100 fortheir use of New York State public highways—excluding toll-paid portionsof the New York State Thruway. The RUT may be calculated based on thedistance (e.g., miles, kilometers) traversed on New York State publichighways and the weight of the vehicle 100. For instance, the RUT mayonly apply to vehicles 100 with a gross unloaded weight over a certainnumber of pounds (e.g., more than 18,000 pounds). In this example, atruck, tractor, and/or other self-propelled vehicle plus the unloadedweight of the heaviest trailer, semitrailer, dolly, and/or other deviceto be drawn by that vehicle plus the maximum load to be carried or drawnby the motor vehicle with a gross unloaded weight over 18,000 pounds maybe subject to the RUT. In another example, the RUT may apply to vehicles100 with an unloaded weight of more than 8,000 pounds or vehicles 100with an unloaded weight of more than 4,000 pounds. Exemplary RUTs areshown in FIGS. 6A and 6B. As will be recognized, a variety of approachesmay be used to adapt to various needs and circumstances.

To track/monitor any applicable RUTs, vehicle owners and/or operatorsmay be required to record (e.g., maintain electronic records for eachtrip, day, week, month and/or quarter of operation of the vehicle 100)information about the operations of each qualified vehicle 100. Therecords may include information about each driving trip, such as thevehicle identification number, the start date of each trip, the end dateof each trip, the start time of each trip, the end time of each trip,the point of origin, the point of destination, the number of roundtrips, the total distance traversed within the jurisdiction, the totaldistance traversed outside the jurisdiction, and/or the total distancetraversed on any roads excluded from the RUT. The records may alsoinclude the total public road distance traversed, the total non-publicroad distance traversed, the total distance traversed within thejurisdiction laden (e.g., with a load or any part of a load), and/or thetotal distance traversed within the jurisdiction unladen (e.g., withoutany load whatsoever). Additional information may also be recorded, suchas odometer data, hubometer data (and any similar data), data regardingany associated bills of lading, waybills, freight bills, invoices,shipping orders, and/or the like.

With the records (e.g., electronic records), owners and/or operators ofqualified vehicles 100 may be required to periodically (e.g., quarterly)file RUT returns. For example, owners and/or operators may be requiredto file quarterly RUT returns based on, for example, their usage ofcertain public roads within the previous quarter.

ii. Fuel Use Taxes (FUTs)

In one embodiment, certain jurisdictions (e.g., countries, regions,states, counties, cities, and/or towns) may impose a fuel use tax (FUT)on particular types of vehicles 100 operating within theirjurisdictions. The purpose of the FUT may be to subject fuel purchasedoutside of the jurisdiction to the same taxes (excise tax, sales tax,and petroleum business tax) as are imposed on fuel purchased and usedinside the jurisdiction. For instance, the FUT may be imposed onqualified vehicles 100 for their use of certain public roads. Thus, aspreviously described, the FUT may exclude fuel, for example, consumed ontoll roads or non-public roads within a jurisdiction. By way of example,if a vehicle owner and/or operator of a qualified vehicle 100 purchasesfuel in New Jersey and delivers equipment to locations in New York fortwo days using all the fuel purchased in New Jersey, the FUT wouldattempt to impose taxes as though the fuel were purchased in New York(excluding fuel consumed on paid portions of the New York StateThruway). Generally, one may be exempt from the FUT if he/she onlypurchases fuel in the relevant jurisdiction and only operates thevehicle 100 within the jurisdiction.

In one embodiment, the FUT may be computed based on the amount (e.g.,gallons or liters) of fuel used to operate qualified vehicles 100, forexample, on public highways in the relevant jurisdiction. Totrack/monitor any applicable FUTs, vehicle owners and/or operators maybe required to record (e.g., maintain electronic records for each trip,day, week, month, and/or quarter of operation of the vehicle)information about the operations of each qualified vehicle 100. Forexample, vehicle owners and/or operators may be required to keep arecord of all fuel purchased and/or consumed for each qualified vehicle100. The records may include information, such as the location of fuelpurchased, the quantity of fuel purchased, and/or the cost of the fuelpurchased. The records may also include the amount of fuel consumedoutside the jurisdiction and/or the amount of fuel consumed within thejurisdiction. Exemplary FUTs are shown in FIG. 8. Additional informationmay also be recorded, such as odometer data, oil pressure data, and/orthe like.

With the records (e.g., electronic records), owners and/or operators ofqualified vehicles 100 may be required to periodically (e.g., quarterly)file FUT returns. For example, owners and/or operators may be requiredto file quarterly FUT returns based on, for example, their fuelconsumption within the jurisdiction.

b. Defined Geographic Areas

In one embodiment, as indicated in Block 500 of FIG. 5, the process maybe begin with a computing entity (e.g., via a user operating a computingentity) defining one or more geographic areas. In one embodiment, thegeographic areas may correspond to countries, regions, states, counties,cities, towns, private land areas, vehicle staging areas, parking lots(e.g., at malls or other establishments), driveways, and/or the like.For example, geographic areas may be defined around the United States,the state of Georgia, Gwinnett County in the state of Georgia, and/orthe like. In one embodiment, the geographic areas may correspond toroads, streets, avenues, toll roads, ways, interstates, and/or the like.For example, each geographic area may be defined around a public road(e.g., substantially around I-285) or a portion of a public road (e.g.,exit and/or entrance ramps on I-75 in Georgia or through out the U.S.).In one embodiment, the geographic areas may correspond to deliveryroutes, bus routes, and/or taxis routes (e.g., driven by deliverydrivers, bus drivers, and/or taxis drivers). The geographic areas may bedefined based on zoning classifications associated with differentgeographic areas (e.g., an office park, industrial park, and/orneighborhood).

According to various embodiments of the present invention, a geographicarea may overlap or reside wholly within another geographic area.Geographic areas may, for example, be as large as an entire country,region, state, county, city, or town (or larger). According to variousembodiments, the geographic areas need not be continuous. In otherwords, a geographic area may specifically exclude an area that wouldotherwise fall within the geographic area (e.g., such that thegeographic area forms a donut or other shape around the excluded area).

The geographic areas may be defined based on any number and/orcombination of factors including, but not limited to, those describedabove. The foregoing examples are therefore provided for exemplarypurposes only and should not be taken in any way as limiting embodimentsof the present invention to the examples provided.

c. Defined Geofences

In one embodiment, once the geographic areas have been defined, acomputing entity (e.g., via a user operating a computing entity) maydefine one or more geofences (Block 505), such as defining a geofencearound a geographic area. The geofences may be defined to surround adefined geographic area, such as surrounding countries, regions, states,counties, cities, towns, interstates, roads, streets, avenues, tollroads, ways, exit and entrance ramps, delivery routes, bus routes, taxisroutes, industrial parks, neighborhoods, off-road areas (e.g., areaswithout paved roads), private land areas, parking lots (e.g., at mallsor other establishments), driveways, and/or the like. The geofences maybe defined, for example, by the latitude and longitude coordinatesassociated with various points along the perimeter of the geographicarea. Alternatively, geofences may be defined based on latitude andlongitude coordinates of the center, as well as the radius, of thegeographic area. Geofences may be as large as an entire country, region,state, county, city, or town (or larger). The geographic areas, andtherefore the geofences, may be any shape including, but not limited to,a circle, square, rectangle, an irregular shape, and/or the like.Moreover, the geofenced areas need not be the same shape or size.Accordingly, any combination of shapes and sizes may be used inaccordance with embodiments of the present invention.

Similarly, a geofence may overlap or reside wholly within anothergeofence. For example, a geofence of a delivery area or town, forinstance, may have geofences defined around private land areas (e.g.,parking lots of malls), off-road areas, and/or toll roads. In oneembodiment, such an embodiment may enable a vehicle owners and/oroperators to track their toll road use, public road use, non-public roaduse, and/or the like within a given jurisdiction.

In one embodiment, once at least one geofence has been defined, thecoordinates (or similar methods for defining the geofenced areas) may bestored in a database associated with, for example, the data collectiondevice 130, portable device 105, and/or monitoring server 110. Thus, asthe vehicle 100 enters and exits the one or more defined geofences, acomputing entity (the data collection device 130, portable device 105,and/or monitoring server 110) can monitor the location of the vehicle100 and trigger/initiate certain events based on the vehicle's 100location.

d. Geofence-Based Collection of Data

In one embodiment, after the one or more geofenced areas (e.g.,geofences) have been defined, the location of the vehicle 100 can bemonitored (Block 510 of FIG. 5). Generally, the location of the vehicle100 can be monitored by any of a variety of computing entities,including the data collection device 130, the portable device 105,and/or the monitoring server 110. For example, as noted above, thevehicle's 100 location at a particular time may be determined with theaid of location-determining devices, location sensors 120 (e.g., GNSSsensors), and/or other telemetry location services (e.g., cellularassisted GPS or real time location system or server technology usingreceived signal strength indicators from a Wi-Fi network). By using thevehicle's 100 location, a computing entity (data collection device 130,portable device 105, or monitoring server 110) can determine, forexample, when the vehicle 100 enters a defined geofence (Block 515 ofFIG. 5).

In one embodiment, as indicated in Block 520 of FIG. 5, in response to(e.g., after) a determination that a vehicle 100 has entered a definedgeofenced area, a computing entity (e.g., the data collection device130, portable device 105, or monitoring server 110) can collect,identify, and/or record/store relevant telematics data (Block 520 ofFIG. 5). For example, the data collection device 130 can collect,identify, and/or record/store fuel data (e.g., first fuel data) thatindicates the fuel level of the vehicle's fuel tank when the vehicle 100enters the geofenced area. Similarly, the data collection device 130 cancollect, identify, and/or record/store distance data (e.g., firstdistance data) that indicates the number of miles or kilometers on thevehicle's odometer and/or hubometer. As will be recognized, a variety ofother telematics data can also be collected, identified, and/orrecorded/stored, such as speed data, geofenced area data (e.g., thetriggering geofence), emissions data, engine data, tire pressure data,oil pressure data, idle data, meteorological data, and/or the like. Inone embodiment, the collected telematics data can be routinely,periodically, and/or continuously be transmitted to, for example, themonitoring server 110.

In one embodiment, after the vehicle 100 has entered the geofenced area,the location of the vehicle 100 can continue to be monitored (Block 525of FIG. 5) by any of a variety of computing entities. By using thevehicle's 100 location, a computing entity can determine, for example,when the vehicle 100 exits the defined geofenced area (Block 530 of FIG.5). As described, this may include using location-determining devices,location sensors 120 (e.g., GNSS sensors), or other telemetry locationservices (e.g., cellular assisted GPS or real time location system orserver technology using received signal strength indicators from a Wi-Finetwork).

In one embodiment, as indicated in Block 520 of FIG. 5, in response to(e.g., after) a determination that a vehicle 100 has exited the definedgeofenced area, a computing entity can collect, identify, and/orrecord/store relevant telematics data (Block 535 of FIG. 5). Forinstance, the data collection device 130 can collect, identify, and/orrecord/store fuel data (e.g., second fuel data) that indicates the fuellevel of the vehicle's fuel tank when the vehicle 100 exits thegeofenced area. Similarly, the data collection device 130 can collect,identify, and/or record/store distance data (e.g., second distance data)that indicates the number of miles on the vehicle's odometer and/orhubometer when the vehicle 100 exits the geofenced area. As described, avariety of other telematics data can also be collected, identified,and/or recorded/stored, such as speed data, emissions data, geofencedarea data (e.g., the triggering geofence), RPM data, tire pressure data,oil pressure data, idle data, meteorological data, and/or the like.Moreover, the collected telematics data can be routinely, periodically,and/or continuously be transmitted to, for example, the monitoringserver 110.

As indicated, telematics data can be collected, identified, andrecorded/stored in an electronic record. For example, in one embodiment,a computing entity (e.g., the data collection device 130, portabledevice 105, or monitoring server 110) can create a new record each timethe ignition of a vehicle 100 is started or each time a vehicle 100enters a geofenced area (e.g., a record may be created for eachgeofenced area in which the vehicle travels). In these examples, therecords can be updated on a routine, periodic, and/or continuous basis.For example, the records can be updated each time the ignition of avehicle 100 is started or turned off and/or each time the vehicle 100enters or exits a geofenced area. In another embodiment, a computingentity (e.g., the data collection device 130, portable device 105, ormonitoring server 110) can create a new record for a given time period,such as each day, each week, each month, and/or each quarter. Thus, anew record can automatically be created when a new time period begins.

In one embodiment, as shown in FIGS. 10 and 11, an electronic record fora trip may include information, such as vehicle identification number,trip start date, trip end date, trip start time, trip end time, point oforigin, and/or point of destination. An electronic record for a trip mayalso include the total distance traversed, total non-toll geofencedistance traversed, total toll geofence distance traversed, totalnon-geofence distance traversed, total public road distance traversed,total non-public road distance traversed, total distance traversedladen, total distance traversed unladen, amount of fuel purchased, dateof fuel purchase, location of fuel purchase, fuel level at point oforigin, fuel level at point of destination, and/or trip fuelconsumption. As will be recognized, a variety of approaches andtechniques can be used to adapt electronic records to a variety of needsand circumstances. In one embodiment, electronic records for trips canbe aggregated into electronic records for days, weeks, months, types ofvehicles, fleets, and/or the like. Additionally or alternatively, eachvehicle 100 may have an electronic record that corresponds to a specifictime period (e.g., each day, week, month, and/or quarter).

In one embodiment, such records can be used to validate and provide anaudit trail of all distances and paths traversed. As will be recognized,a variety of other techniques and approaches can be used to adapt tovarious needs and circumstances.

e. Exemplary Estimated Taxes

In one embodiment, by collecting telematics data (e.g., distance data),a computing entity can determine the estimated distance traversed by thevehicle 100 while operated within relevant areas within the jurisdiction(Block 540 of FIG. 5). For example, this can be determined based atleast in part on the electronic records for each trip, day, week, month,and/or quarter of operation of the vehicle 100. Using the electronicrecords for a prescribed period of time (e.g., day, week, month, and/orquarter), a computing entity (e.g., monitoring server 110) can determinean estimated FUT for the vehicle 100, a vehicle type, a fleet, and/or anowner and/or operator (Block 545 of FIG. 5). For example, as shown inFIG. 7, an estimated RUT calculation may involve a variety of factors,such as the total number of miles driven within the jurisdiction, thetotal taxable number of miles driven within the jurisdiction (e.g.,excluding the miles driven on non-public roads), the applicable taxrate, and/or a variety of other factors. Using such information, thecomputing entity (e.g., monitoring server 110) can determine theestimated RUT as defined by the relevant jurisdiction for the prescribedtime period (e.g., as shown in FIG. 7). In one embodiment, the computingentity can also generate and transmit an RUT return to the appropriatejurisdictional (e.g., government) entity. As will be recognized, avariety of approaches and techniques may be used to determine estimatedRUTs.

In one embodiment, by collecting telematics data (e.g., fuel data), acomputing entity can determine the estimated amount of fuel consumed bythe vehicle 100 while operated within the jurisdiction (Block 540 ofFIG. 5). For example, this can be determined based at least in part onthe electronic records for each trip, day, week, month, and/or quarterof operation of the vehicle 100. Using the electronic records for aprescribed period of time (e.g., day, week, month, and/or quarter), acomputing entity (e.g., monitoring server 110) can determine anestimated FUT for the vehicle 100, a vehicle type, a fleet, and/or anowner and/or operator (Block 545 of FIG. 5). For example, as shown inFIG. 9, an estimated FUT calculation may involve a variety of factors,such as the total number of miles driven within the jurisdiction, thetotal taxable number of miles driven within the jurisdiction, theaverage miles per gallon/liter achieved for the miles driven within thejurisdiction, the amount of fuel purchased within the jurisdiction forthe relevant time period, and the amount of fuel purchased outside thejurisdiction for the relevant time period, the net amount of taxablefuel, the applicable tax rate, and/or a variety of other factors. Usingsuch information, the computing entity (e.g., monitoring server 110) candetermine the estimated FUT as defined by the relevant jurisdiction forthe prescribed time period (e.g., as shown in FIG. 9). In oneembodiment, the computing entity can also generate and transmit an FUTreturn to the appropriate jurisdictional (e.g., government) entity.

As will be recognized, a variety of approaches and techniques may beused to determine estimated RUTs and FUTs. For example, the estimatedRUTs and FUTs may be determined for one or more jurisdictions, one ormore geofenced areas, one or more days, one or more weeks, one or moremonths, one or more quarters, one or more years, and/or one or moreother time periods. Further, the estimated RUTs and FUTs may bedetermined, for instance, on a vehicle 100, vehicle type, fleet, and/orowner and/or operator basis. Accordingly, the foregoing examples areprovided for illustrative purposes only and should not be taken in anyway as limiting embodiments of the present invention to the examplesprovided.

f. Alternative Embodiments

In one embodiment, as a result of vehicle 100 travel, the monitoringserver 110 (or other computing entity) may be configured for identifyingpaths traveled by a vehicle 100 that have not been plotted, have beenplotted incorrectly, or otherwise stored in the monitoring server's mapsand for updating the monitoring server's maps to include the identifiedpaths (herein “unknown paths”). The unknown paths identified by themonitoring server 110 may include, among other things, new roads inrecently constructed residential neighborhoods and non-public roads orlanes in commercial areas. For example, because known methods forupdating GPS-based maps are time consuming, the monitoring server's maps(e.g., an electronically navigable base map stored on the monitoringserver database) often do not include newly constructed roads beforethey are traveled by a vehicle 100. Similarly, as GPS-based maps oftendo not include non-public road paths, vehicles 100 frequently travelalong lanes in the parking lot of a large shopping center or roadssurrounding a large distribution center that are not included in themonitoring server's maps.

According to various embodiments, the monitoring server 110 isconfigured to identify unknown paths and update the monitoring server'smaps based on telematics data captured from the vehicle 100 by the datacollection device 130, for example. As noted earlier herein, in variousembodiments, the data collection device 130 is configured to capturetelematics data that includes data indicating the vehicle's location asthe vehicle 100 travels along a given path (e.g., GPS coordinatescaptured by a location sensing device). As a result, the travel path ofthe vehicle 100 at any point during the course of an operational day canbe determined and plotted on a map based on the captured telematicsdata. Accordingly, the monitoring server 110 may be configured toidentify telematics data captured while the vehicle 100 is (or was)traveling along an unknown path (or an incorrectly plotted path) andplot the unknown path (or correct the incorrectly plotted path) based onthe identified telematics data.

The telematics data corresponding to an unknown path (or an incorrectlyplotted path) can generally be identified by determining the vehicle'sdistance from the nearest known road at the time a telematics datarecord is captured by the data collection device 130. For example, FIG.12A illustrates a road 1205 along which the vehicle 100 may travel. Asshown in FIG. 12B, the road 1205 may be represented as a known road inthe monitoring server's maps by a string of road data points 1200, eachof which is associated with data indicating its respective location(e.g., GPS-compatible latitude and longitude data). According to variousembodiments, the road data points 1200 may be positioned along the pathof the road 1205 and generally spaced a distance D1 apart from oneanother.

FIG. 12C illustrates a plurality of location data points 1210 capturedas the vehicle 100 traveled along the road 1205. In the illustratedembodiment of FIG. 12C, the distance between a particular location datapoint 1210 and the nearest road data point 1200 is indicated as thedistance D2. Although the distance between the location data points 1210themselves may vary depending on the speed of the vehicle 100 andfrequency of the telematics data capture, each location data point 1210is necessarily proximate at least one of the road data points 1200.Indeed, as long as the vehicle 100 is traveling along the known road1205, the distance D2 between any given location data point 1210 and thenearest road data point 1200 will not exceed the distance D1 (i.e., thedistance between adjacent road data points 1200). Accordingly, invarious embodiments, location data points 1210 having a distance D2 fromthe nearest road data point 1200 that is greater than the distance D1will correspond to travel along an unknown path (or an incorrectlyplotted path).

For example, FIG. 12C illustrates an unknown road 1220 that extendsthrough a new residential neighborhood constructed adjacent the knownroad 1205. FIG. 13B shows a plurality of location data points 1210captured as the vehicle 100 traveled along the known road 1205, turnedfrom the known road 1205 onto the unknown road 1220, and then returnedto the known road 1205. As shown in FIG. 13B, the location data points1210 captured along the unknown road 1220 have a distance D2 from theirnearest road data point 1200 that is greater than the distance D1. Assuch, the location data points 1210 corresponding to the unknown road1220 can be identified and connected to form a new path 1215representing the unknown road 1220. The location data points 1210comprising the new path 1215 can then be stored in the monitoringserver's maps in order to update the maps to reflect the newlyconstructed road 1220. As will be appreciated from the descriptionherein, the process can be used to identify and store unknown publicroads, private roads, parking lot lanes, or other unknown paths orincorrectly plotted paths traveled by the vehicle 100.

According to various embodiments, the monitoring server 110 isconfigured to run the monitoring server 110 in response to a userrequest (e.g., a request received via a graphical user interface). FIG.14 illustrates steps executed by the monitoring server 110 to update themonitoring servers' maps according to one embodiment. Beginning at step1400, the monitoring server 110 identifies the first telematics datarecord in the operational data set loaded by the monitoring server 110and defines this first data record as the “current data record.” Next,at step 1405, the monitoring server 110 determines the vehicle's 100distance from the nearest known road at the time of the current datarecord's capture. In one embodiment, the monitoring server 110 executesstep 1405 by determining the location of the vehicle at the time thecurrent data record was captured (e.g., based on a location data pointin the current data record), identifies the nearest point on a knownroad in relation to the vehicle's location (e.g., based on the locationdata associated with the road data points in the monitoring server'smaps), and calculates the distance between the vehicle's location andthe nearest road data point.

Next, at step 1410, the monitoring server 110 determines whether thedistance calculated in step 1405 exceeds a predefined threshold distance(e.g., the average distance D1 between road data points in themonitoring server's maps). If the distance calculated in step 1405 doesnot exceed the predefined threshold, the monitoring server 110 moves tostep 1420. If the distance calculated in step 1405 does exceed thepredefined threshold, the monitoring server 110 moves to step 1415,where it flags the current data record as a “new path point” (e.g., byassociating the current data record with metadata indicating it is a newpath point).

Next, at step 1420, the monitoring server 110 determines whether thereare additional telematics data records in the operational data setloaded by the monitoring server 110. If there are additional telematicsdata records, the monitoring server 110 moves to step 1425, where itidentifies the next telematics data record, stores it as the currentdata record, and repeats steps 1405-1420. If there are no additionaltelematics data records, the monitoring server 110 moves to step 1430,where it identifies strings of consecutive new path points (e.g., thetelematics data records flagged as such) and stores the string of newpath points as a new known path in the monitoring server's maps.

According to various embodiments, the monitoring server 110 may befurther configured to permit a user to name, format, or otherwise modifynew known paths identified by the monitoring server 110. For example, incertain embodiments, the monitoring server 110 may be configured suchthat a user can designate a new known path as a private road, publicroad, parking lot lane, or other path type. The monitoring server 110may then be configured to store the new known path as the designatedpath type in the monitoring server's maps.

In other embodiments, steps 1405-1415 of FIG. 14 may the accomplished bythe data collection device 130. For example, as noted earlier herein,the data collection device 130 may be configured to recognize vehicleevents characterized by data generated by GPS-sensors or other locationsensing devices, such as a vehicle traveling onto a known road (e.g., aroad recognized by a GPS device) and a vehicle traveling off of a knownroad (e.g., exceeding a certain predefined distance from a known road).As such, the data collection device 130 may be configured toautomatically flag telematics data records as new path points at thetime they are captured. Likewise, the monitoring server 110 may beconfigured to identify telematics data records flagged by the datacollection device 130 and execute steps 1400 and 1420-1430 accordingly.

IV. Conclusion

Many modifications and other embodiments of the inventions set forthherein will come to mind to one skilled in the art to which theseembodiments of the invention pertain having the benefit of the teachingspresented in the foregoing descriptions and the associated drawings.Therefore, it is to be understood that the embodiments of the inventionare not to be limited to the specific embodiments disclosed and thatmodifications and other embodiments are intended to be included withinthe scope of the appended claims. Although specific terms are employedherein, they are used in a generic and descriptive sense only and notfor purposes of limitation.

1. A computer-implemented method for recording telematics data for avehicle based one or more geofences, the method comprising: uponinitiation of an ignition of the vehicle, automatically monitoring, by aglobal positioning system located within the vehicle, a location of thevehicle, wherein the global positioning system determines when thevehicle enters or exits one or more geofenced areas during one or moretime periods, wherein the one or more geofenced areas are stored in adatabase of a monitoring system as one of non-public traversed area orpublic traversed area; automatically monitoring, by a fuel sensor, afuel amount corresponding to when the vehicle enters or exists the oneor more geofenced areas during the one or more time periods;determining, by a monitoring server, a total fuel amount of fuelconsumed by the vehicle during the one or more time periods based on thefuel amount corresponding to when the vehicle enters or exits one ormore geofenced areas; determining, by the monitoring server, areportable amount of fuel consumed by the vehicle during the one or moretime periods, wherein determining the reportable amount of fuelcomprises excluding a non-public traversed area amount of fuel consumedby the vehicle within a first geofenced area of the one or moregeofenced areas and including a public traversed area amount of fuelconsumed by the vehicle within a second geofenced area of the one ormore geofenced areas from the total amount of fuel; and generating, bythe monitoring server, a trip record for display via a display device,wherein the trip record includes at least the total amount of fuel andthe reportable amount of fuel.
 2. The method of claim 1, the methodfurther comprising determining an estimated fuel use tax based at leastin part of the reportable amount of fuel.
 3. The method of claim 2,wherein the trip record further includes the estimated fuel use tax. 4.The method of claim 1, wherein the fuel amount corresponding to when thevehicle enters or exists the one or more geofenced areas during the oneor more time periods comprise data indicating fuel levels of thevehicle's fuel tank.
 5. The method of claim 1, the method furthercomprising identifying, using the global positioning system, a distancetraversed by the vehicle in the one or more geofenced areas based on thedetermination of when the vehicle enters or exits the one or moregeofenced areas during one or more time periods.
 6. The method of claim5, the method further comprising determining an estimated road use taxfor operating the vehicle within the one or more geofenced areas basedat least in part on the distance traversed by the vehicle in the one ormore geofenced areas.
 7. The method of claim 5, wherein the distancetraversed by the vehicle includes a second distance traveled within thesecond geofenced area and does not include a first distance traveled inthe first geofenced area.
 8. The method of claim 6, wherein theestimated road use tax is further based at least in part on a weight ofthe vehicle.
 9. The method of claim 6, wherein the trip record furtherincludes the estimated road use tax.
 10. A system for recordingtelematics data for a vehicle based one or more geofence, the systemcomprising: memory; and one or more processors collectively configuredto: upon initiation of an ignition of the vehicle, automaticallymonitor, via a global positioning system located within the vehicle, alocation of the vehicle to determine when the vehicle enters or exitsone or more geofenced areas during one or more time periods, wherein theone or more geofenced areas are stored in a database as one ofnon-public traversed area or public traversed area; automaticallymonitor, via a fuel sensor, a fuel amount corresponding to when thevehicle enters or exists the one or more geofenced areas during the oneor more time periods; determine a total fuel amount of fuel consumed bythe vehicle during the one or more time periods based on the fuel amountcorresponding to when the vehicle enters or exits one or more geofencedareas; determine a reportable amount of fuel consumed by the vehicleduring the one or more time periods, wherein the reportable amount offuel is determined by excluding a non-public traversed area amount offuel consumed by the vehicle within a first geofenced area of the one ormore geofenced areas and including a public traversed area amount offuel consumed by the vehicle within a second geofenced area of the oneor more geofenced areas from the total amount of fuel; and generate atrip record for display via a display device, the trip record includingat least the total amount of fuel and the reportable amount of fuel. 11.The system of claim 10, wherein the one or more processors are furtherconfigured to determine an estimated fuel use tax based at least in partof the reportable amount of fuel.
 12. The system of claim 11, whereinthe trip record further includes the estimated fuel use tax.
 13. Thesystem of claim 10, wherein the one or more processors are furtherconfigured to identify a distance traversed by the vehicle in the one ormore geofenced areas based on the determination of when the vehicleenters or exits the one or more geofenced areas during one or more timeperiods.
 14. The system of claim 13, wherein the one or more processorsare further configured to determine an estimated road use tax foroperating the vehicle within the one or more geofenced areas based atleast in part on the distance traversed by the vehicle in the one ormore geofenced areas.
 15. They system of claim 14, wherein the estimatedroad use tax is further based at least in part on a weight of thevehicle.
 16. The system of claim 14, wherein the distance traversed bythe vehicle includes a second distance traveled within the secondgeofenced area and does not include a first distance traveled within thefirst geofenced area.
 17. The system of claim 14, wherein the triprecord further includes the estimated road use tax.
 18. A non-transitorycomputer-readable medium comprising code executable by a processor to:upon initiation of an ignition of a vehicle, automatically monitor, viaa global positioning system located within the vehicle, a location ofthe vehicle to determine when the vehicle enters or exits one or moregeofenced areas during one or more time periods, wherein the one or moregeofenced areas are stored in a database as one of non-public traversedarea or public traversed area; automatically monitor, via the globalpositioning system, a distance data corresponding to when the vehicleenters or exists the one or more geofenced areas during the one or moretime periods; determine total distance traversed by the vehicle duringthe one or more time periods based on the distance data corresponding towhen the vehicle enters or exits one or more geofenced areas; determinea reportable distance traversed by the vehicle during the one or moretime periods, wherein the reportable amount of distance traversed isdetermined by excluding a non-public traversed area distance traversedby the vehicle within a first geofenced area of the one or moregeofenced areas and including a public traversed area distance traversedby the vehicle within a second geofenced area of the one or moregeofenced areas from the total amount of fuel; and generate a triprecord for display via a display device, the trip record including atleast the total distance traversed and the reportable distancetraversed.
 19. The computer-readable medium of claim 17, the codeexecutable by a processor further to determine an estimated road use taxfor operating the vehicle within the one or more geofenced areas basedat least in part on the reportable distance traversed.
 20. Thecomputer-readable medium of claim 18, wherein the estimated road use taxis further based at least in part on a weight of the vehicle.